<body>
<?php
$header_msg = "iron wrought golem cookies";
include_once('header.inc');
?>
	<h1>Notes</h1>
	<h2>Task requirements</h2>
	<p>
		we are supposed to write a worklog for the project,
		which is supposed to be delivered together with a
		report of the work with and the project
	</p>
	<H3>noootes</H3>
	<P>
		put any other notes here.
	</P><P>
		the header file enables every page to have their own 'H1' message in the
		green area of the header, called '$header_msg'. and its own title called
		'$title_msg'. we could put a favicon as well if anyone wants to do that.
	</P><P>
		maybe change mypage.php to profile.php? makes more sense. also add
		public profile page for users to see info on other users.
	</P><P>
		okay, added comments, they display upside down for some reason, but its
		too late to continue now. DO UPDATE when starting tomorrow, as this
		commit is one of the bigger ones as of now.
	</P>
	<h3>Front page[index.html]</h3>
	<div>
		<p>
			<b>any one, on visit:</b> show all last blog entries<br>
			<b>any one, at will:</b> show most read last 14 days<br>
			<b>any one, at will:</b> show most commented last 14 days<br>
			<b>admin, on login:</b> list all offensive content<br>
			<b>any user, on login:</b> users blogpost overview<br>
		</p>
	</div>
	<!--
	Divisor: 'any' content
	Paragraph: textual content
	-->
	<h2>TODO</h2>
	<p>
		<datagrid>
			<li>fix header.inc so it has username with mypage link and being pretty</li>
			<LI>fix first register_login message in index from reg.php</LI>
			<LI>add option to ask for moderator rights on my page.
			this should trigger a request for action from all mods,
			and be fulfilled when one either accepts or denies the request.</LI>
			<!-- the above point is not rigid for any real website, should
			require more than one mod to acknowledge/decline any request as such,
			and even then it is not a proper system for it, but this small
			project it works adequately -->
			<LI>edit mypage user-info</LI>
		</datagrid>
	</p>
	<h2>links</h2>
	<p>
		google code repo: <a href="http://code.google.com/p/imt2291wwwtechv12/">
			http://code.google.com/p/imt2291wwwtechv12/</a><br>
		google docs report: <A HREF="https://docs.google.com/document/d/1ebtOONbpxpQWn9BtnmhJUUTC17e14ZBkLIcoS9nV75s/edit">
			https://docs.google.com/document/d/1ebtOONbpxpQWn9BtnmhJUUTC17e14ZBkLIcoS9nV75s/edit</A><BR>
		facebook for websites: <a href="https://developers.facebook.com/docs/guides/web/">
			https://developers.facebook.com/docs/guides/web/</a><br>
		google plus API: <a href="http://code.google.com/apis/accounts/docs/OpenID.html">
			http://code.google.com/apis/accounts/docs/OpenID.html</a><br>
		google authentication API: <a href="http://code.google.com/apis/accounts/">
			http://code.google.com/apis/accounts/</a><br>
		user-account-system guide: <A HREF="http://webdevrefinery.com/forums/topic/3280-how-to-make-a-user-account-system/">
			http://webdevrefinery.com/forums/topic/3280-how-to-make-a-user-account-system/</A>
	</p>
	<h2>LOG</h2>
	<h3>tuesday 21022012</h3>
	<p>
		had first work meeting. setup a code.google.com subversion repo,
		and have barely started gathering our resources. we will start
		work tomorrow after the IMT2282 test.
	</p>
	<h3>tuesday 28022012</h3>
	<p>
		started adding in functionality for reading config files,
		so we wont need to have DB authentication in clear text in
		our changelogs. this is not something we need or should
		spend time polishing, but I(thomas) found it to be a good
		way to start the day.
	</p>
	<h3>monday 12032012</h3>
	<p>
		Real work as a group has begun, in due time. We're working
		hard to get the database working. We realize it's not easy,
		of us have any real experience with php or even html. This
		will not be an easy week. We managed to get the databases up
		and working by the end of the day. In addition, we have a page
		with some sub-pages up and running. Tomorrow, we will work on
		login and registartion features, and hopefully actually being able
		to post on the blog.
	</p>
	<h3>tuesday 13032012</h3>
	<p>
		Worked all day. We have the login and registration features working
		as intended, and the pages know which user is logged in, if any. We're
		pretty short on time, but we hope to make it. It will require hard work
		from all of us the next couple of days, though.
	</p>
	<h3>wednesday 14032012</h3>
	<p>
		Not as many hours of work as yesterday. We can now post entries to a database
		and display them, induvidually or all of them on the frontpage. Some work has
		been done on commenting posts, but it's not quite finished yet.
	</p>
	<h3>thursday 15032012</h3>
	<p>
		today we made the offensiv post flagging work, put up the rest of the
		different ways of sorting and showing blogposts, and we realized that we
		are probably meant to be implementing one of the many html5/javascript
		editors rolling around out there. it has been atleast partially
		implemented. we also added post and comment deletion, and editing of posts
		and user details. we also found the requirements to be rather lacking of
		boundaries, this includes, but is not limited to, the one between
		requirements and extras.
	</p>
	<?php include_once('footer.inc'); ?>
